What this PR does 📖

• add shuttle hotspot
• enables announcing to mesh by default
• enables auto push by default.
• Add an option for preloading bootstrap or peers.

Which issue(s) this PR fixes 🔨

Special notes for reviewers 🗒️

Additional comments 🎤

• this PR introduces a light node to assist building out a mesh of peers for announcing identity and other data. Ideally this would work along side shuttle as trusted but light nodes which would accept, verify and subscribe to identity topics to allow messages to propagate over the network. While shuttle does this in its own way, this allows for anybody outside a (future) trusted node to be able to help build the network out eventually without needing to run shuttle directly.
• This can be used as a relay, but ideally to be used as a fallback (under a future configuration)
• If an identity does not announce in a specific timeframe, their subscription is removed and their cache is removed until the identity is later announced back and go through the verification process.
• This does not intend to store anything on disk besides key pair and configuration options for relay (if used) so upon restarting the node would require the user to announce their identity, in which case would go through the verification process.
• These nodes, once trusted and bootstrapping of shuttle is implemented , could be apart of shuttle bootstrap providers that is supplied to clients upon initial bootstrap to shuttle to allow clients to participate in the network, discover identities announced over the network outside of shuttle.
• There may be a form of shedding of identities stored in the task if the logic consumes more resources in the future. I.e, removing out dated identities, performing reachability, either directly or through relay, how often the identity updates their identity to determine if temporary shedding and blacklisting is needed, etc